Very great! 👍

The standard is officially called ISO/IEC 15444-1:2016 etc. I would not drop the IEC part.

In the section Assignment operators I would write a := a + 1 etc. instead of a = a + 1 etc.

@retokromer I'm following the practice for referencing ISO/IEC standards as done at https://xml2rfc.tools.ietf.org/public/rfc/bibxml2/. In the cases here ISO/IEC standards use anchors that are prefixed with only ISO..

The change for QuantizationTablePerContext adds some \
which show up in the final output, these where not there before, are they intended?

the indention of the elements in the 2nd column is inconsistet, for example the br element between the Frame and SliceHeader

in SliceHeader() you randomize the indention, sar_den and the following if() are at the same indentio level before a02463a and 1 space different after.

@michaelni I couldn't see the character you meant in #25 (comment). But I found an extra | character in there and removed it in fed0e6f.

Indentation noted in #25 (comment) and #25 (comment) is fixed in fbe46cc.

I think I've updated according to all comments. Please re-review. I can also squash the codeblock commits together if easier.

Comment 25 was about a backslash
about combining and spliting commits, please combine bugfixes with commits introducing the bug so no known issues are added while keeping commits seperated. Note this would be much easier if you submit things early as then little rebasing of later commits would be needed

Commits are squashed to eliminate introducing/fixing bugs and for readability.

Thanks
indention in Parameters() is random,
";" placement at end of lines is random too everywehre
space placement in for() / while() and if() mismatches
space placement in function args and () is inconsistent
space placement around array indexes is inconsistent
Most of this exists priot to the patch some is made worse by it though like the indention in Parameters()

@dericed It´s not the link itself, but the wording I see that hurts me: the title reads wrong in markdown this way.

I updated the Parameters indentation. For the rest which exists prior, let's leave for a later PR.

@retokromer can you move the question on iso citation style to cellar.

The change to SliceContent() is not correct, same for Line(), the indention in Parameters() also is still not correct

I reviewed codeblocks for indentation and order. PR is updated.

Pixel() is wrongly indented after te first patch in Line()

I fixed Pixel() indentation in Line() and resolved merge conflicts.

And rebased to remove the commit on resolving merge conflicts. Should be ready.

merged 1 patch, Is it intended that the "left-align" patch skips the Suffix Examples table ?

Updated to left-align the Suffix Examples table.

@retokromer, regarding #25 (comment), I agree but didn't want to extend the scope of the PR, so I filed it under #27

I added a commit to get the references back to the ffv1.pdf since that output doesn't gather them automatically from the xml2rfc process. If of interest, then I can merge that with f6d5db0.

@michaelni, anything else needed for the remaining commits?

4504e25 make the table rather hard to read in the pdf. The individual terms are hard to see in the flowing text that reaches into the same first column

4504e25 is updated to a7cedb0, which is a better compromise between the output of mmark/xml2rfc and pandoc.

Is it intended that a130bbc causes litteral "@!" to be shown in the the output (pdf in this case) ?

The "@!" is part of mmark's syntax to identify a reference in the RFC output, though this shows as a literal in the PDF output. I suppose we could add a 'sed s/[@!/[/g' to the Makefile before the PDF output is rendered. ?

+1 for filtering out mmark’s own syntax before rendering the PDF.

The solution suggested in #25 (comment) is implemented in ccd33f2#diff-b67911656ef5d18c4ae36cb6741b7965R15. I also dropped a few commits from the PR that were already cherrypicked.

LGTM

merged